Updating transition scheduling logic #446
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
scazan
force-pushed
the
transition-scheduling-logic
branch
from
b286ee8 to
85dd429
Compare
scazan
force-pushed
the
transition-scheduling-logic
branch
from
0b7df2f to
6b61024
Compare
scazan
force-pushed
the
transition-scheduling-logic
branch
from
649ba02 to
f60bf87
Compare
- Parallelize pMap calls in updateTransitionsForProcess.ts - Consolidate DB queries in transitionMonitor.ts using JOIN - Make concurrency consistent (5) across files - Create transitions when publishing draft instances - Add comprehensive transition processing tests
scazan
force-pushed
the
transition-scheduling-logic
branch
from
9847e93 to
d20aae9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates the transition scheduling system to properly handle the new DecisionSchemaDefinition template format. Transitions are now created based on phase rules rather than for every phase, and scheduling uses the correct date field of endDate.
If an update occurs, we remove any transitions that are no longer needed UNLESS they have already completed in which case we need to keep them for historical reasons as they were part of a process.